Paths are the central result of an assignment (Paths in PrT and PuT). In the timetable-based assignment (Timetable-based assignment) a PuT path is described through a sequence of path legs which each represent one of the following activities.
- Change of location from one stop point to another by using a specific vehicle journey
- Change of location from origin zone via a connector and links to a stop point or from there to destination zone with a PuT-Walk TSys
- Transition from one stop point to another with a PuT-Walk TSys
- Change of location by using a PuT-Aux TSys
Because each of the used vehicle journeys is known, the path has a time reference (Network objects of the line hierarchy). Each of its path legs starts and ends at a precise time. This is called a connection.
If the option Save paths – as connections has been selected for the assignment (Using Visum: Settings for saving PuT assignment results), these connections become visible in the PuT path leg list.
Alternatively, a path can be described without specifying vehicle journeys in detail. In this case only the time profile is known, which was used for a change of location via a PuT line (Network objects of the line hierarchy). The departure and arrival times of each path leg are then relative times relating to the beginning of the path, completely analog to the difference between vehicle journey and time profile. Such a path described by the used time profiles and relative times is called a route.
Naturally, routes are suitable especially to aggregate display of recurring connections at regular timetables. Two connections at different headway times which otherwise run the same, are combined to the same route. This usually requires considerably less memory space.
When executing the timetable-based assignment with option Save paths – as routes (Using Visum: Settings for saving PuT assignment results), individual connections are still determined and loaded internally. These are, however, only saved as aggregated routes after the assignment. Reference is lost to the individual vehicle journeys as well as their exact departure times. The PuT path leg list then shows the relative times for departure and arrival, and the optional relations to the first and after the last vehicle journey item are empty. Because the network elements are loaded prior to discarding the connections, time-based volumes can still be determined.
The third option Save paths – do not save (Using Visum: Settings for saving PuT assignment results) results in that no path information is saved after ending the assignment. Only the derived values of the network object volumes and also skim matrices are retained after the assignment. This way, path-based post-assignment analyses are not possible – especially no flow bundle calculation. PuT path list and PuT path leg list also remain empty, however, time-based volume values are also possible with this option.
Due to its differing user model, headway-based assignment (Headway-based assignment) not even internally determines connections but routes. The option Save paths as connections can be selected, however, but at headway-based assignment routes are saved in either case (or nothing). These are formally equal to those routes determined by the timetable-based assignment and can be output in the same way as PuT path list or PuT path leg list.
The Table 161 shows the path legs which result from a timetable-based assignment in example Example.ver. In this case, the paths were saved as connections.
|
Origin zone |
Destination zone |
Path index |
Path leg index |
Passenger trips |
From stop point |
To stop point |
TP indicator |
Departure |
|
100 |
200 |
1 |
|
25000 |
10 |
40 |
|
6:10:00 AM |
|
|
|
|
1 |
|
|
10 |
OrigConn |
6:10:00 AM |
|
|
|
|
2 |
|
10 |
20 |
BUS1 1_H > 1 |
6:10:00 AM |
|
|
|
|
3 |
|
20 |
20 |
Transfer |
6:22:00 AM |
|
|
|
|
4 |
|
20 |
40 |
TRAIN 1_H > 1 |
6:25:00 AM |
|
|
|
|
5 |
|
40 |
|
DestConn |
6:41:00 AM |
|
100 |
200 |
2 |
|
14000 |
10 |
40 |
|
6:10:00 AM |
|
|
|
|
1 |
|
|
10 |
OrigConn |
6:10:00 AM |
|
|
|
|
2 |
|
10 |
40 |
BUS1 1_H > 1 |
6:10:00 AM |
|
|
|
|
3 |
|
40 |
|
DestConn |
6:55:00 AM |
|
100 |
200 |
3 |
|
18000 |
10 |
40 |
|
6:55:00 AM |
|
|
|
|
1 |
|
|
10 |
OrigConn |
6:55:00 AM |
|
|
|
|
2 |
|
10 |
40 |
BUS1 1_H > 1 |
6:55:00 AM |
|
|
|
|
3 |
|
40 |
|
DestConn |
7:40:00 AM |
|
100 |
200 |
4 |
|
16000 |
10 |
40 |
|
7:25:00 AM |
|
|
|
|
1 |
|
|
10 |
OrigConn |
7:25:00 AM |
|
|
|
|
2 |
|
10 |
20 |
BUS1 1_H > 1 |
7:25:00 AM |
|
|
|
|
3 |
|
20 |
20 |
Transfer |
7:37:00 AM |
|
|
|
|
4 |
|
20 |
40 |
TRAIN 1_H > 1 |
7:45:00 AM |
|
|
|
|
5 |
|
40 |
|
DestConn |
8:01:00 AM |
|
100 |
200 |
5 |
|
17000 |
10 |
40 |
|
7:25:00 AM |
|
|
|
|
1 |
|
|
10 |
OrigConn |
7:25:00 AM |
|
|
|
|
2 |
|
10 |
40 |
BUS1 1_H > 1 |
7:25:00 AM |
|
|
|
|
3 |
|
40 |
|
DestConn |
8:10:00 AM |
Table 161: Path legs after a timetable-based assignment (paths saved as connections)
For the same assignment, Table 162 shows the path legs if the paths were saved as routes.
|
Origin zone |
Destination zone |
Path index |
Path leg index |
Passenger trips |
From stop point |
To stop point |
TP indicator |
Departure |
|
100 |
200 |
1 |
|
25000 |
10 |
40 |
|
00:00:00 |
|
|
|
|
1 |
|
|
10 |
OrigConn |
00:00:00 |
|
|
|
|
2 |
|
10 |
20 |
BUS1 1_H > 1 |
00:00:00 |
|
|
|
|
3 |
|
20 |
20 |
Transfer |
12:12:00 AM |
|
|
|
|
4 |
|
20 |
40 |
TRAIN 1_H > 1 |
12:15:00 AM |
|
|
|
|
5 |
|
40 |
|
DestConn |
12:31:00 AM |
|
100 |
200 |
2 |
|
49000 |
10 |
40 |
|
00:00:00 |
|
|
|
|
1 |
|
|
10 |
OrigConn |
00:00:00 |
|
|
|
|
2 |
|
10 |
40 |
BUS1 1_H > 1 |
00:00:00 |
|
|
|
|
3 |
|
40 |
|
DestConn |
12:45:00 AM |
|
100 |
200 |
3 |
|
16000 |
10 |
40 |
|
00:00:00 |
|
|
|
|
1 |
|
|
10 |
OrigConn |
00:00:00 |
|
|
|
|
2 |
|
10 |
20 |
BUS1 1_H > 1 |
00:00:00 |
|
|
|
|
3 |
|
20 |
20 |
Transfer |
12:12:00 AM |
|
|
|
|
4 |
|
20 |
40 |
TRAIN 1_H > 1 |
00:20:00 |
|
|
|
|
5 |
|
40 |
|
DestConn |
12:36:00 AM |
Table 162: Path legs after a timetable-based assignment (paths saved as routes)
